feat(elements): Add backup_code verification strategy - #3627
Conversation
🦋 Changeset detectedLatest commit: 69b3384 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| setConsoleError: ({ event }) => { | ||
| if (process.env.NODE_ENV === 'development') { | ||
| assertActorEventError(event); | ||
| if (process.env.NODE_ENV !== 'development') { |
There was a problem hiding this comment.
Removed throw as it puts users into a completely irrecoverable state even if FieldError or GlobalError are present.
| }; | ||
| } | ||
| if (type === 'password' && shouldValidatePassword) { | ||
| } else if (type === 'backup_code') { |
There was a problem hiding this comment.
The code name has a number of predefined assumptions which don't work for backup codes.
The backup_code name circumvents those assumptions while still maintaining the required field name of code.
|
!snapshot |
|
Hey @tmilewski - the snapshot version command generated the following package versions:
Tip: Use the snippet copy button below to quickly install the required packages. npm i @clerk/chrome-extension@1.1.1-snapshot.v64cb67f --save-exact
npm i @clerk/clerk-js@5.7.3-snapshot.v64cb67f --save-exact
npm i @clerk/elements@0.10.0-snapshot.v64cb67f --save-exact
npm i @clerk/clerk-expo@1.2.4-snapshot.v64cb67f --save-exact
npm i gatsby-plugin-clerk@5.0.0-beta.45 --save-exact
npm i @clerk/ui@0.1.5-snapshot.v64cb67f --save-exact |
3 participants
Description
Adds
backup_codeverification strategyFixes SDK-1852
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change